This repository was archived by the owner on Feb 28, 2026. It is now read-only.
Use set for efficient retry status code filtering#266
Closed
Stephen0512 wants to merge 1 commit intoAzure:masterfrom
Closed
Use set for efficient retry status code filtering#266Stephen0512 wants to merge 1 commit intoAzure:masterfrom
Stephen0512 wants to merge 1 commit intoAzure:masterfrom
Conversation
Member
|
Hello, this project is now deprecated and no longer accept PR and releases. If you encounter any issues using the Azure SDK for Python, please file an issue on https://github.com/Azure/azure-sdk-for-python/issues |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves the implementation of
ClientRetryPolicyby replacing list-based membership checks with a set when computing retryable HTTP status codes.Previously, the retry status code list was generated by checking membership against a list of safe status codes, resulting in repeated O(n) lookups for 999 times. This change introduces a set for the safe status codes, enabling O(1) average-time membership checks while preserving the existing behavior and semantics.
The issue was identified during an ongoing research project.